Why are these changes needed?

This PR partially resolves #49342 (specifically addressing the first bullet point regarding Cluster view navigation).

The Problem: Currently, when viewing the Nodes table in the Cluster view, the worker process name is plain text. There is no quick way to jump to the details of a specific Actor running on that node without manually copy-pasting IDs into the search bar.

The Solution: This PR updates the WorkerRow component inside NodeRow.tsx so that the worker's process name (the cmdline string) now acts as a direct <Link> to the Actor Detail page (if the worker is hosting an Actor).

Architectural Code Choices

During implementation, I had to account for several backend data structures exported by Ray:

1. Array Extraction: worker.coreWorkerStats is passed as an array to the frontend. The logic extracts coreWorkerStats[0] to safely access the ID.
2. "Nil" ID Handling: If a worker is not an actor, Ray does not set actorId to null/undefined. Instead, it passes a "Nil" ID (a string of 32 or 40 fs). I added an explicit check against this ffff... string to prevent linking users to non-existent actor pages.
3. Task IDs are 1:N: We cannot natively link generic task workers to a specific /tasks/{taskId} page from this view. A worker process is long-lived and executes many tasks sequentially, so the backend does not expose a single taskId in the top-level worker stats.
4. The Fallback: If the worker is not an Actor, it safely falls back to linking to /cluster/nodes/{nodeId} (the Node Detail page) to preserve navigation utility.

Related issue number

Resolves #49342

Testing Instructions

1. Start a local Ray cluster.
2. Run a script that spawns a long-running Actor:

import ray
import time

ray.init()

@ray.remote
class DummyActor:
    def do_work(self):
        time.sleep(3600)

a = DummyActor.remote()
a.do_work.remote()

while True:
    time.sleep(1)